Prerequisites for Mule ESB Monitoring Agent

Unlock the full potential of your Mule ESB and MuleSoft Anypoint Platform with the Nodinite Mule ESB Monitoring Agent. This page outlines everything you need to get started—ensuring a smooth, secure, and efficient monitoring experience for your integration landscape.

Architecture overview: The Nodinite Monitoring Agent supports both on-premise and cloud/hybrid MuleSoft environments for maximum flexibility.

You can deploy the agent on-premise using TCP/IP for local network access, or in the cloud/off-site using Service Bus Relaying ('Azure Relay FAQs').

We recommend installing the agent close to the Nodinite Core Services. This guide focuses on local network setups, typically on the Nodinite application server.

Mule ESB Application (ZIP)

For Mule ESB version 3.x, use this option for on-premise environments. Mule version 4.x leverages public CloudHub APIs.

The Nodinite Mule ESB Monitoring Agent communicates with a Nodinite-specific Mule ESB Application that you install on each Mule Server Instance you wish to monitor. This application provides direct access to the Mule ESB run-time, ensuring comprehensive monitoring and insight.

Software Requirements

This section applies to the Nodinite application server where you will install the Nodinite Mule ESB Monitoring Agent via the Portal or as a Windows Service.

v7.4.0 and later: .NET 10 Hosting Bundle required. Installed via Nodinite Portal automated installation.
v6.0 - v7.3.x: .NET Framework 4.8 or later
v5.4: .NET Framework 4.6.2 or later
v4.8 (Legacy): Supported for on-premise environments where v7 upgrade is not possible
Versions before v5.4: .NET Framework 4.5.2 or later (deprecated)

What Windows User Rights does the Nodinite Mule ESB Monitoring agent require?

The agent is installed as a Windows Service usually on the Nodinite application server. Virtual machines are supported.

Service Account Options ^{New 7.4.0}:

• Group Managed Service Account (gMSA) - Recommended for automated password management. See Configure Group Managed Service Accounts (gMSA) for setup instructions.
• Traditional Account - Use a local named account or, preferably, a domain account.
  • Follow the 'How to set logon as a Windows service right' user guide for detailed instructions.

What Cloudhub user rights does the Nodinite Mule ESB Monitoring agent require?

This section is applicable for version 4.x.

The Nodinite Mule ESB Monitoring Agent requires the Cloudhub Admin right. Apply this setting to each environment.

To enable monitoring of the Anypoint instance, apply the Cloudhub Admin right to each environment.

What Mule ESB User rights does the Nodinite Mule ESB Monitoring agent require?

This section is applicable for version 3.x.

The Nodinite Mule Monitoring Application (Zip file) needs to be installed into the Mule ESB server instance (repeat for each node to be monitored)

What Firewall settings does the Nodinite Mule ESB Monitoring agent require?

Where you install the Nodinite Mule ESB Monitoring Agent in relation to the Nodinite Monitoring Service, your on-premise Mule ESB 3.x servers, and the Anypoint Platform determines your firewall configuration. The diagram shows every host involved, with the agent on its own server; each arrow starts at the side that opens the connection.

Network diagram: the Monitoring Service calls the agent; the agent calls the Nodinite Mule ESB Monitoring Application on each Mule 3.x server and the Anypoint Platform APIs for Mule 4.x and CloudHub. Dashed arrows are optional hops.

Note

When the agent runs on the Core Services Server (the typical installation, and the one we recommend), you need no firewall rule between the Monitoring Service and the agent.

Between the Monitoring Service and the Mule ESB Monitoring Agent

The Monitoring Service opens every connection; the agent never calls it. On Windows Server, Nodinite v7 hosts the agent as its own IIS web site, on a port you set per environment in the Nodinite Portal (Servers step).

Option: Service Bus Relaying (cloud or hybrid)

Use Service Bus Relayed connections when Nodinite and the agent are on different networks. Both sides connect outbound to the Azure Relay namespace, so neither server needs an inbound rule. Nodinite uses the same principle as the on-premises data gateway; see 'Adjust communication settings for the on-premises data gateway' and the 'Azure Relay FAQs'.

Between the Mule ESB Monitoring Agent and the Mule ESB 3.x servers

Required only for Mule ESB 3.x. The agent calls the Nodinite Mule ESB Monitoring Application (ZIP) installed on each Mule server; open the port inbound on every Mule server you monitor.

Between the Mule ESB Monitoring Agent and the Anypoint Platform

Required for Mule 4.x and CloudHub. The agent calls the Anypoint Platform APIs of your control plane. All traffic is outbound HTTPS; MuleSoft needs no inbound rule. Allow the hostname of your control plane, as listed in Anypoint Platform hostnames and allowlists.

Tip

CloudHub Authentication: The agent requires the CloudHub Admin right in each environment to monitor; see What Cloudhub user rights does the Nodinite Mule ESB Monitoring agent require?.

Between the servers and DNS

Important

Stateful Firewalls: Most Windows Firewall implementations are stateful, so response traffic for established outbound connections is allowed automatically. The inbound response rules above are for reference and troubleshooting.

Next Steps

Install Mule Monitoring Agent

Related Topics

Add or manage a Monitoring Agent Configuration
Monitoring
Administration